Comprehensive flight planning tool

ABSTRACT

A system for providing a flight planning tool is disclosed. The system may include at least one memory device for storing flight information and one or more hardware processors. The one or more hardware processors may be configured to provide an Application Program Interface (API) for facilitating communication between the system and at least one of a client device and one or more third-party devices, receive, via the API, a request including first information related to a flight, collect, via the API and based on the first information, second information from one or more third-party devices, generate flight trip data based on the first and second information, wherein the flight trip data includes information and graphics associated with the flight, and provide, via the API, one or more user interfaces to the client device for communicating the flight trip data.

PRIORITY CLAIM

This application claims priority under 35 U.S.C. § 119 to U.S.Provisional Application No. 62/107,071, filed on Jan. 23, 2015, U.S.Provisional Application No. 62/137,327, filed on Mar. 24, 2015, and U.S.Provisional Application No. 62/073,425, filed on Oct. 31, 2014, each ofwhich is expressly incorporated herein by reference in its entirety.

TECHNICAL FIELD

The disclosed embodiments generally relate to flight planning, and moreparticularly, to providing a comprehensive flight planning tool forassisting general aviation pilots with planning aviation flights throughthe customized integration of information.

BACKGROUND

Modern flight planning has continued to evolve from early individualweb-based applications that separately supplied a general aviation pilotwith flight information, such as weather, aircraft performanceinformation, airport directories, and fundamental route planning to moreall-in-one-solutions. For example, mobile, in-cockpit Electronic FlightBags (EFBs) provide some information relevant to a flight, such asreal-time weather and traffic information via wireless access to remotedevices. But while current systems like EFBs may provide mobile accessto some available information, there is a need for a single, customizedsource for all critical and pertinent information necessary for a pilotto plan and execute a flight, as well as to integrate the informationacross other available platforms.

SUMMARY

In one aspect, the present disclosure is directed to a system forproviding a flight planning tool. The system may include at least onememory device for storing flight information and one or more hardwareprocessors. The one or more hardware processors may be configured toprovide an Application Program Interface (API) for facilitatingcommunication between the system and at least one of a client device andone or more third-party devices, receive, via the API, a requestincluding first information related to a flight, collect, via the APIand based on the first information, second information from one or morethird-party devices, generate flight trip data based on the first andsecond information, wherein the flight trip data includes informationand graphics associated with the flight, and provide, via the API, oneor more user interfaces to the client device for communicating theflight trip data.

In another aspect, the present disclosure is directed to a method ofproviding a flight planning tool. The method may include generating anApplication Program Interface (API) for facilitating communicationbetween a flight planning system and at least one of a client device andone or more third-party devices, receiving, via the API, a requestincluding first information related to an upcoming flight, collecting,via the API and based on the first information, second information fromone or more third-party devices, generating flight trip data based onthe first and second information, the flight trip data includinginformation and graphics associated with the upcoming flight, andproviding, via the API, one or more one or more user interfaces to theclient device for communicating the flight trip data.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the disclosed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate disclosed embodiments and,together with the description, serve to explain the disclosedembodiments. In the drawings:

FIG. 1 is a block diagram of an exemplary system consistent withdisclosed embodiments;

FIG. 2 is a block diagram of an exemplary server, consistent withdisclosed embodiments;

FIG. 3 is a block diagram of another exemplary system, consistent withdisclosed embodiments; and

FIG. 4 is a flowchart of an exemplary flight information distributionprocess, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Reference will now be made in detail to the disclosed embodiments,examples of which are illustrated in the accompanying drawings. Whereverconvenient, the same reference numbers will be used throughout thedrawings to refer to the same or like parts.

Disclosed embodiments pertain to a comprehensive flight planning tool,which may take the form of an integrated suite of flight planningproducts. The flight planning tool may be a single-source online datafusion of all necessary resources for a general aviation pilot toaccurately and competently plan a flight in a general aviation aircraft.Further, the flight planning tool may allow information to be easilyintegrated with third-party software.

FIG. 1 is a diagram illustrating an exemplary system 100 for performingone or more operations consistent with the disclosed embodiments. In oneembodiment, system 100 may include a flight planning system 110, aclient device 120, a third-party device 130, and a network 140. Thecomponents and arrangement of the components included in the system 100may vary. Thus, the system 100 may further include other components thatperform or assist in the performance of one or more processes consistentwith the disclosed embodiments.

Flight planning system 110 may include one or more computing systemsthat are configured to execute software instructions stored on one ormore memory devices to perform one or more operations consistent withthe disclosed embodiments. Flight planning system 110 may include one ormore of a server, a computer, an embedded system, or a dedicatedhardware device. In certain embodiments, flight planning system 110 maybe configured as a particular apparatus, system, and the like based onthe storage, execution, and/or implementation of the softwareinstructions that perform one or more operations consistent with thedisclosed embodiments.

In an exemplary embodiment, flight planning system 110 may includehardware and/or software components configured to create, store, andtransmit a variety of flight planning tools. For example, flightplanning system 110 may include hardware devices configured to gatherinformation which may be useful to a pilot or individual associated withaviation. For instance, flight planning system 110 may include (or beconfigured to communicate with) devices that include weather data,airport data, aircraft data, pilot data, etc. Flight planning system 110may collect this information and perform one or more processes to makeit available to a user. For example, flight planning system 110 may beconfigured to provide the information to client device 120 and/or thirdparty device 130.

Client device 120 may be one or more computing systems that areconfigured to execute software instructions for performing one or moreoperations consistent with the disclosed embodiments. In someembodiments, client device 120 may be one or more of a mobile device(e.g., a tablet, smartphone, laptop etc.), a desktop computer, a server,an embedded system, a dedicated hardware device, etc. Client device 120may include one or more processors configured to execute softwareinstructions stored in memory, such as memory included in client device120. Client device 120 may include software that, when executed by aprocessor, performs known network-related communication and contentdisplay processes. For instance, client device 120 may execute browsersoftware that generates and displays interface screens including contenton interface hardware (e.g., a display device) included in, or connectedto, client device 120.

In one embodiment, client device 120 may be a laptop or desktop computerconfigured to communicate with flight planning system 110 (e.g., vianetwork 140). Client device 120 may be configured to execute softwareinstructions to display an online flight planner generated by flightplanning system 110. In one embodiment, the online flight planner may bea web-based application (e.g., website, applications, widget, etc.)through which client device 120 may provide information to a user (e.g.,information collected by flight planning system 110) and requestinformation from flight planning system 110 (e.g., generation of aflight plan).

In another embodiment, client device 120 may be a tablet or smartphoneconfigured to store and/or execute one or more mobile applications(“apps”). For example, client device 120 may be configured to run aflight planning app, which may make flight planning system 110accessible to a user (e.g., receive requests based on user input,display information received from flight planning device 10, etc.).

Third-party device 130 may be one or more computing systems associatedwith a third-party. Third-party device 130 may include one or morecomputing systems that are configured to execute software instructionsfor performing one or more operations consistent with the disclosedembodiments. For example, third-party device 130 may be as a server,computer, laptop, mobile device (e.g., tablet, smartphone, etc.), andembedded system, a dedicated hardware device, etc. While one third-partydevice 130 is shown in FIG. 1, it should be understood that system 100may include a plurality of third-party devices 130, each associated withthe same or different third-parties.

In one aspect, third-party device 130 may be associated with athird-party that determines, collects, and/or stores information relatedto aviation. For example, third-party device 130 may be associated witha weather forecaster, an aircraft manufacturer, an airport, an aircraft,an aviation regulatory entity (e.g., FAA and the like), etc., andgenerate periodic or real-time information, including pilot information,aircraft information, travel routes, custom waypoints, weather briefs,light plans, bulletins, and/or other information. In this way, flightplanning system 110 may receive real-time information throughcommunication with a selected third-party device 130.

Other information generated by third party device 130 may includereal-time alerts and/or flight restrictions. For example, third partydevice 130 may generate weather alerts associated with particularregions, airports, or flight paths as weather patterns change. Thirdparty device 130 may also generate alerts communicating critical flightinformation, such as temporary flight restrictions (TFR), notices toairmen (NOTAM), closed airport notices, etc. Such information may beofficial (published) notices from an authoritative entity (e.g., FAA) ornon-official notices (e.g., stadium TFRs).

In one aspect, flight planning system 110 may be configured to generateNOTAMs based on flight planning information, including informationreceived from one or more of the user, flight planning system 110, andthird-party devices 130. For example, flight planning system 110 may beconfigured to generate NOTAMs based on a current location, futurelocation (e.g., based on logged flight plans), calendar events, futureflight plans, and/or other ascertainable parameters. Custom NOTAMs maybe generated based on user preferences that may be stored in connectionwith system 100 (e.g., in a user database). For example, userpreferences may include certain information to receive notificationsabout, certain times to receive notifications, certain geographicregions in which to receive notifications, and/or other preferences.

NOTAMs may also or alternatively be generated and displayed to the userautomatically based on current and/or future submitted flight planinformation. For example, a database of open notifications may be kepton or in connection with system 100 as notifications are generated(e.g., by agencies, by users, by airports, etc.). When a user's currentor future flight plan parameters overlap parameters associated with anotice in the notification database, a NOTAM may be generated to notifythe user of the relevant information. In another aspect, users may beallowed to search the notification database (e.g., using keywordsearching, dropdown menus, chronologically, based on location, etc.)through flight planning system 110 or directly through a third-partysource, to search or brows for particular notices or types of notices.

In another aspect, NOTAMs may be generated in conjunction with a flightsafety calculator. For example, flight planning system may include or beconnectable to (e.g., via a third-party device) a computational programconfigured to determine a safety rating based on certain flight planinformation and other available information. In one aspect, the flightsafety calculator may be configured to receive current and futureweather information, ground condition information, user-providedinformation, and/or other information and generate a safety score basedon such inputs. For example, weather information may include indicia ofseverity, location, altitude, and timing of unfavorable weather, whichmay be compared to flight plan information, such as flight pathinformation, departure and arrival locations and timing, altitude,and/or other information. Based on the comparison, NOTAMs may begenerated (e.g., official or unofficial), and communicated to clientdevice 120 to alert the user of potential weather issues. The flightsafety calculator may also receive inputs from third-party sources, suchas FAA resources, the National Weather Service, other users, and/orother sources, which may be included as factors in the comparison andgeneration of NOTAMs.

In another aspect, third-party device 130 may be associated with athird-party that provides information to a user through client device120. For example, third-party device 130 may be associated with anentity that provides an aviation tool (e.g., a mobile app) that may beaccessed by client device 120. In some embodiments, flight planning tool110 may communicate with third-party device 130 to integrate informationand resources to enhance the aviation tool provided by the third-party.

In another aspect, third-party device 130 may include installed cockpitnavigation equipment, wireless cockpit equipment, and/or other flighttools. Such third-party devices 130 may include wired or wirelesscommunication interfaces configured to permit communication with clientdevice and flight planning system via network 140. Information generatedby such third-party devices may include flight routes, air traffic,weather information, and/or other information useful or planning flightmaneuvers.

Network 140 may be any type of network (e.g., a communication network)configured to provide communications between components of system 100.For example, network 140 may be any type of network (includinginfrastructure) that provides communications, exchanges information,and/or facilitates the exchange of information, such as the Internet, aLocal Area Network, Near Field Communication (NFC), WiFi, Bluetooth®, orother suitable connection(s) that enables the sending and receiving ofinformation between the components of system 100. In other embodiments,one or more components of system 100 may communicate directly through adedicated communication link(s) (not shown), such as a link betweenflight planning system 110 and client device 120.

FIG. 2 shows an exemplary server 211 for implementing embodimentsconsistent with the present disclosure. In an exemplary embodiment,server 211 may correspond to flight planning system 110. It should beunderstood, however, that variations of server 211 may correspond toclient device 120, third-party device 130, and/or components thereof.

In one embodiment, server 211 may include one or more processors 221,one or more memories 223, and one or more input/output (I/O) devices222. According to some embodiments, server 211 may be an embedded systemor similar computing device(s) that generate, maintain, and provide website(s) and/or mobile applications consistent with disclosedembodiments. Server 211 may be standalone, or it may be part of asubsystem, which may be part of a larger system. For example, server 211may represent distributed servers that are remotely located andcommunicate over a network (e.g., network 140) or a dedicated network,such as a LAN.

Processor 221 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, or any of variousprocessors manufactured by Sun Microsystems. The disclosed embodimentsare not limited to any type of processor(s) configured in server 211.

Memory 223 may include one or more storage devices configured to storeinstructions used by processor 221 to perform functions related todisclosed embodiments. For example, memory 223 may be configured withone or more software instructions, such as program(s) 224 that mayperform one or more operations when executed by processor 221. Thedisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, memory 223 mayinclude a single program 224 that performs the functions of the server211, or program 224 could comprise multiple programs. Additionally,processor 221 may execute one or more programs located remotely fromserver 211. For example, flight planning system 110, client device 120,and/or third-party device 130, may, via server 211, access one or moreremote programs that, when executed, perform functions related tocertain disclosed embodiments. Memory 223 may also store data 225 thatmay reflect any type of information in any format that the system mayuse to perform operations consistent with the disclosed embodiments.

I/O devices 222 may be one or more devices configured to allow data tobe received and/or transmitted by server 211. I/O devices 222 mayinclude one or more digital and/or analog communication devices thatallow server 211 to communicate with other machines and devices, such asother components of system 100.

Server 211 may also be communicatively connected to one or moredatabase(s) 226. Server 211 may be communicatively connected todatabase(s) 226 through network 140. Database 226 may include one ormore memory devices that store information and are accessed and/ormanaged through server 211. By way of example, database(s) 226 mayinclude MS SQL, Oracle™ databases, Sybase™ databases, or otherrelational databases or non-relational databases, such as Hadoopsequence files, HBase, or Cassandra. The databases or other files mayinclude, for example, data and information related to the source anddestination of a network request, the data contained in the request,etc. Systems and methods of disclosed embodiments, however, are notlimited to separate databases. In one aspect, system 200 may includedatabase 226. Alternatively, database 226 may be located remotely fromthe system 200. Database 226 may include computing components (e.g.,database management system, database server, etc.) configured to receiveand process requests for data stored in memory devices of database(s)226 and to provide data from database 226. In this way, database(s) 226may be a centralized data store configured to enable real-time datasharing and synchronization with devices connected to system 100.

FIG. 3 is a diagram illustrating an exemplary configuration of thecomponents of system 100, including various additional components andfeatures thereof. It should be understood that the configuration ofsystem 100 depicted in FIG. 3 is exemplary, and that otherconfigurations, including additional and/or alternative components andfeatures are possible.

In an exemplary embodiment, flight planning system 110 may includefeatures configured to generate a flight plan and/or provide the flightplan and/or aviation-related information to client device 120. Forexample, flight planning system 110 may include a plurality of modules315 and a flight plan application programming interface 318 (API).Modules 315 may serve as data sources, configured to collect and storeinformation, as well as to generate and store additional informationand/or customized tools. Flight plan API 318 may be an exemplaryinterface through which flight planning system 110 may communicate withclient device 120 and third-party device 130. That is, flight plan API318 may be configured to allow flight planning system 110 to communicatewith client device 120 and/or third-party device 130 over network 140.While flight plan API 318 is depicted and described as one interface, itshould be understood that flight plan API 318 my include a plurality ofinterfaces, such as an internal flight plan API for communicating withclient device 120 (e.g., through a website or mobile applicationassociated with flight planning system 110) and an external flight planAPI for communicating with client device 120 (e.g., through athird-party website or mobile application) and/or third-party device130.

API 318 include a REST-based (representational state transfer)architecture or another type of architecture, if desired. API 318 may beconfigured to communicate various types of information, such as flightplant, pilot information, aircraft information, user-defined waypoints,user generated content, etc. API 318 may be device-agnostic. That is,API 318 may be configured to communicate successfully with deviceshaving various operating platforms and/or communication protocols. API318 may include encryption protocols, such as Secure Sockets Layer(SSL), to provide for secure data transmissions.

As shown in FIG. 3, client device 120 may include or embody one or moreof a plurality of client devices 325. Client devices 325 may includedevices operated by users. The users may operate client devices 325 tocause client devices 325 to communicate with flight planning system 110via flight plan API 318 and/or third-party device 130 (e.g., throughnetwork 140). Client devices 325 may receive information from flightplanning system 110 and/or third-party device 130 and display it withassociated interface hardware. Further client devices 325 may beconfigured to receive user input, and provide the user input informationto flight planning system 110 and/or third-party device 130, such as tocause those devices to provide certain information back to clientdevices 325.

Third-party device 130 may be connected to network 140 such thatthird-party device 130 may communicate with flight plan API 318 and/orclient devices 325. As shown in FIG. 3, third-party device 130 mayinclude a plurality of third-party devices 130, which each may beassociated with a different third-party entity, as described above.

In an exemplary embodiment, modules 315 may include at least a flightplanning module 332, a weather module 334, and an airport module 336.For the purposes of this disclosure, “modules” (also known as “engines”)may be implemented in software, hardware, firmware, a mix of any ofthose, or the like. For example, if the disclosed “modules” areimplemented in software, they may be stored in a memory associated withflight planning system 110. Processors, I/O devices, and memory devicesmay be utilized to perform processes to implement and facilitateoperations of modules 315. Thus, modules 315 may include codeinstructions executable by one or more processors, alone or in variouscombinations with other modules disclosed in this or other embodiments.For example, flight planning module 332 may be configured to interactwith weather module 334, and/or other modules of flight planning system110, shown or not shown in FIG. 3, to perform functions consistent withdisclosed embodiments. In other embodiments, if the disclosed “modules”are implemented in hardware, they may comprise an embedded system orother dedicated hardware configured by machine code, assembly code, orthe like to interact with other modules of flight planning system 110 toperform functions consistent with disclosed embodiments.

Flight planning module 332 may be configured to generate flight tripdata based on information received through other modules or from otherdevices (e.g., via API 318). Flight trip data may include anyinformation or data pertaining a flight (e.g. a past flight, a presentflight, a future flight) or aviation in general. Flight trip data mayinclude, for example, flight plans, weather information, aircraftinformation (e.g., profile, maintenance, manifest, schedule, etc.),departure information (e.g., date, time, location, etc.), destinationinformation (e.g., date, time, location, etc.), calendar information,travel information (e.g., hotels, rental cars, dining, attractions,etc.), and/or other information. For example, flight planning module 332may be configured to execute software instructions to determine a routefor a potential aviation flight. Flight planning module 332 maycommunicate with other modules 315 to collect information that may beused to calculate a flight route. Flight planning module 332 may alsocommunicate with third-party devices 130 (e.g., via flight plan API 318)to collect information. Flight planning module 332 may provide agenerated flight plan to client device 110 for display and use by auser.

In some embodiments flight planning module 332 may include variousfeatures configured to provide an interactive flight plan. For example,flight planning module 332 may include a flight planning engine, arouting engine, and a graphics engine. The routing engine may determinea route for the flight and the graphics engine may generate interactivecharts and weather displays. The flight planning engine may combine theroute and graphics to generate an interactive flight plan for a user.

Weather module 334 may be configured to track and store informationrelated to weather that may affect aviation, such as by providing accessto a collection of real-time, forecasted and predictive weather productsvia API 318 and/or client devices 120, 325. For example, weather module334 may generate forecasts and predictions based on collected weatherdata or may receive completed forecasts and predictions. Weather module334 may receive data and/or forecasts from third-party devices 130(e.g., via flight plan API 318). For example, weather module 334 mayaccess a weather forecast system such as Aircraft Owners and PilotsAssociation (AOPA) Weather. Weather module 334 may be configured toprovide weather information to flight planning module 332 for use ingenerating a flight plan. Collected weather data and/or predictiveweather information may be displayed on client devices 120, 325 in oneor more of textual and graphical formats (e.g., via user interfacesconfigured to display text or a graphical image configured to convey amessage).

Support data module 336 may be an additional module or modulesconfigured to collect, generate, and/or store additional informationthat may be pertinent to aviation, such as information that may be usedby flight planning module 332 to create a flight plan. For example,support data module 336 may provide information related to airports,aircrafts, airlines, pilots, social media, news, aviation entities(e.g., FAA, AOPA, etc.), and the like. Support module 336 may connect tothird-party devices 130 associated with this information (e.g., viaflight plan API 318) to gather and store information that may be used byflight planning module 332 and/or provided to client device 110 and/or athird-party device 130.

Exemplary features of support data module 336 may include flightplanning resources such as an airport directory (e.g., through access toa full AOPA airports directory), weight and balance information,temporary flight restrictions, user-generated content, pilot andaircraft logbooks, manuals and instructions, calendars, etc. Further,while depicted and described with respect to support data module 336, itshould be understood that other components of flight planning system 110may additionally, alternatively, and/or work in combination with supportdata module 336 to provide these features.

The airport directory information may include, for example, airportprocedures, airport diagram thumbnails and corresponding full-sizediagrams (e.g., FAA airport diagrams), airport services, available fuel,communication frequencies, business information, and/or otherinformation. Information generated by an airport (e.g., by its staff) ora governing body (e.g., FAA) pertaining to the airport may also beavailable in the airport directory information. For example,information, including comments, messages, bulletins, and/or otherremarks, from airport staff or the FAA, runway obstruction notices, ortemporary procedural changes may be posted the directory in connectionwith a particular airport.

Directory information may be viewed in one or more different formats viaa user interface. For example, director information may be vied infull-page views, thumbnails, printable formats (e.g., kneeboard formats,full page, etc.), screen overlays, etc. Overlays may be positioned overother screens and include information relevant to the underlying screen.For example, an overlay over screen showing a travel route may includeinformation indicative of, for example, fuel available along the route,airports along the route, airport services along the route, etc.

Other information useful for planning or carrying out flight plans mayalso be available for browsing, searching, printing, and sharing (e.g.,via email, social media, etc.). For example database information and/orthird-party source information may include resources, such ascommunication frequencies, waypoint information, fuel statistics, dateand time information (e.g., time zone information, date conventions,etc.), Morse Code information, ground communication frequencies, and/orother information. Such information may be available to viewelectronically, for printing (e.g., full view, kneeboard format, etc.),or for sharing.

Such information may also include advertising information displayed viauser interfaces or overlays. For example, advertisement interfaces maybe displayed (e.g., based on a user selection of a certain interfaceview, based on a determination that a flight has ended, etc.) that areconfigured to redirect users to websites, apps, or other interfaces toview additional information.

In another aspect, users may be allowed to monitor aircraft loading withrespect to passenger and cargo loads. For example, signals indicative ofweight and/or balance information generated by sensors (e.g.,contact/pressure sensors, optical sensors, infrared sensors, barcodesensors, laser sensors, etc.) associated with passenger seats, cargocompartments, and/or other aircraft structural components may bereceived by flight planning system 110 from third-party devices 130(e.g., via API 318) and translated into loading data. The loading datamay include weight and/or balance values, qualitative indicia (e.g.,colors, shapes, textures, etc.), and or other visual indicator that maybe displayed via interface hardware. The loading data may be displayedon client devices 120, 325 in conjunction with a library known aircraftgeometries and capacities. In this way, the user may be able to quicklyidentify opportunities to optimize weight distribution and/or balanceand confirm that loading values are within ranges, for example, asprovided by an aircraft pilot's operating handbook (POH).

Users may be allowed to print or fill out existing or downloadablechecklist forms on user interfaces. In this way, users may be allowed toeasily check off pre-flight, in-flight, and post-flight checklist items.Users may be allowed to access a library of common checklists for commonaircrafts (e.g., stored in conjunction with third-party device 130, auser database, memory hardware, or other media storage) that may beviewed or downloaded via mobile application device 354. Users may alsobe allowed to modify existing checklists, create new checklists fromavailable templates, or create new checklists from scratch in via one ormore user interfaces in conjunction with interface hardware. Forexample, one of modules 315 may be configured (e.g., in conjunction withone or more processors), to generate a user interface configured toreceive input indicative of checklist template modifications or arequest to store a new template.

In addition to modules 315, flight planning system 110 may include or beconnected to at least one database 340. Database 340 may containrelevant pilot, aircraft, and flight planning information that may beused by one or more components of system 100, such as flight planningmodule 332. Flight plan API 318 may be configured to retrieveinformation from database 340 for modules 315, client devices 325,and/or third-party devices 130. In an exemplary embodiment, database 340may be an SQL database, but is not limited thereto.

Client devices 325 may include any client computing device configured tocommunicate with flight planning system 110 and/or a third party device130. In an exemplary embodiment, client devices 325 may include onlineflight planner devices 352, mobile application devices 354, andthird-party application devices 356. It should be understood that theserepresentations of client devices 325 are made for convenience ofdiscussion, and that they may overlap (i.e., a mobile application device354 and a third-party application device 356 may be the same device).

Online flight planner devices 352 may be client devices 352 that areconfigured to communicate with flight planning system 110 to provide aweb-based flight planning tool to a user. For example, online flightplanner devices 352 may be laptop, desktop computer, notebook, tablet,smartphone, smartwatch, etc. configured to access a website (or otherweb-based application) provided by flight planning system 110. Thewebsite my provide access to a comprehensive flight planning toolprovided by flight planning system 110.

Mobile application devices 354 may be client devices 352 that areconfigured to execute a mobile flight planning application. The mobileflight planning application may be a similar tool to the websiteaccessible by online flight planner devices 352; however, it may becustomized for use by a mobile device, including software that may bestored by mobile application devices 354. The mobile flight planningapplication may also provide access to a comprehensive flight planningtool provided by flight planning system 110.

Mobile application device 354 may include memory hardware, processinghardware, and interface hardware. Other features of mobile applicationdevice 354 may include a location device (e.g., a GPS device) configuredto determine a location of mobile application device 354, and may alsoinclude a connection device configured to wirelessly connect to network140 (e.g., a cellular communication device, Wi-Fi Device, Bluetooth®device, etc.). It is noted that other client devices 325, such as onlineflight planner devices 352 and third-party application devices 356, mayinclude components described with reference to mobile application device354, such as memory hardware, processing hardware, interface hardware,and any other hardware or software described with reference to mobileapplication device 354.

Mobile application device 354 may be configured to execute a mobileapplication stored in memory hardware. For example, mobile applicationdevice 354 may be a smartphone or tablet configured to run a mobileoperating system (e.g., iOS, Android, etc.) which may be compatible witha variety of mobile applications provided by third-party providers. Inan exemplary embodiment, the mobile application is a comprehensiveflight planning tool. In other words, mobile application device 354 maybe configured to provide a comprehensive flight planning tool to a userof mobile application device 354 via mobile application.

It is noted that mobile the application is not limited to use withmobile application device 354. The mobile application may be used withother client devices, such as online flight planner devices 352,third-party application devices 356, and/or other client devices 325.The mobile application may be appropriately configured for used withonline flight planner devices 352, mobile application devices 354,third-party application devices 356, or any other client device 325. Forexample, the mobile application may be configured to be used inconjunction with web-based or web-browsing software, self-containedapplication software (i.e., an app), or third-party software accessiblethrough web-based or self-contained software.

Mobile application device 354 may operate in conjunction with otherdevices in order to provide the comprehensive flight planning tool. Forexample, mobile application device 354 may communicate with flightplanning system 110 and one or more third-party devices 130 via network140. In one example, mobile application device 354 may communicate withflight planning system 110 to initially install mobile application 450.

Third-party application devices 356 may be client devices 325 that aresimilar to online-flight planner devices 352 and/or mobile applicationdevices 354. For example, third-party application devices 356 may haveweb access and/or be configured to execute a mobile application.Regardless, third-party application device 356 may differ in that theyconnect to a third-party device 130 for receiving information through awebsite or mobile application. For example, third-party applicationdevices 356 may include client devices 325 that store and execute one ormore social media platforms provided by a third-party device 130. In anexemplary embodiment, flight planning system 110 may be configured tocommunicate with the associated third-party device 130 such that flightplanning information may be combined with the third-party application toprovide an integrated service to a user through a third-partyapplication device 325.

Client devices 325 may include data storage hardware configured to storeinformation locally on client devices 325. Client devices 325 may beconfigured to store any type of information that may be used onconnection with system 100, such as pilot information, aircraftinformation, user preferences, waypoint information, flight information,airport directory information, and or other information. Storedinformation may include information received from third-party devices130, information generated by flight planning system 110, andinformation received from the user. In this way, client devices 325 maybe configured to provide online and offline access to informationrelevant to carrying out flight plans and/or performing other tasks.Such information may also or alternatively be stored on other datastorage devices associated with system 100 that are accessible viaclient devices 325 when access to all or portions of network 140 isunavailable.

The exemplary disclosed embodiments allow for the accumulation of allinformation that may be useful in aviation, such as flight planning orflying. The configuration and components (e.g., flight plan API 318) ofthe disclosed embodiments allow this information to be routed to variouscomponents where it may be used to generate additional information,graphics, data sets, etc., which may in turn be provided to and used bya user, either directly through a website or mobile application orindirectly through integration with a third-party service. Exemplaryprocesses that the components of system 100 may perform to provide theseand other features are described below.

FIG. 4 is a flowchart of an exemplary flight information distributionprocess 400. In one embodiment, one or more of the components of system100 may perform process 400 to provide flight information to user ofclient device 120. The flight information may include any informationrelated to aviation that may be useful to the user, and may be more thaninformation alone. For example, the flight information may include aninteractive flight plan including information and generated graphicsconfigured to be displayed through an interface.

Flight planning system 110 may receive a request for flight information(step 410). Client device 120 may generate the request based on inputfrom a user using interface hardware. Client device 120 may transmit therequest to flight planning system 110, such as through flight plan API318. For example, a user may operate client device 120 to interact witha website or mobile application provided by flight planner device 110,which may include a request for flight information, such as a flightplan for an upcoming flight. The request may include information forcreating the flight plan, such as information identifying a pilot,aircraft, origin, destination, schedule, etc. Flight planning system 110may route the request to the appropriate component(s), such as modules315.

Modules 315 may store a received request and gather other informationthat may be used to respond to the request (step 420). For example,flight planning module 332 may receive a request for flight informationthat includes a flight plan. Modules 315 may execute softwareinstructions to perform one or more processes to gather the informationnecessary to generate the flight plan. For example, flight plan module332 may communicate with weather module 334 to receive weather forecastinformation for the time period around the planned flight. Flight planmodule 332 may communicate with one or more support data modules 336 togather any temporary flight restriction alerts that may affect theflight. Flight plan module 332 may also communicate with database 340 tocollect airport information (e.g., maps, locations, etc.), historicalweather information, pilot information, etc.

Flight planning system 110 may create a request response (step 430). Therequest response may be the flight information requested in step 410,for example, in a form that may be sent to client device 120. In theexample of client device 120 requesting a flight plan, flight planningmodule 332 may generate the interactive flight plan based on theinformation gathered in step 420. Flight planning system 110 maysubsequently send the request response to client device 120 (step 440).For example, flight planning system 110 may send a generated flight planto client device 120 via flight plan API 318. In other embodiments,flight planning device may supply requested data to client device 120,and client device 120 may use the requested data to generate aninteractive flight plan.

In some embodiments, flight planning system 110 may integrate flightinformation across platforms and devices (step 450). For example, flightplanning system 110 may sync, in real-time, a generated flight plan,in-flight information (e.g., speed, altitude, etc.), and the like acrossmultiple devices and components (e.g., online flight planner device,mobile application devices, third-party devices, etc.). In anotherexample, flight information may be integrated into third-party services,such as social media, logbooks, calendars, etc. For example, flightplanning system 110 may communicate with a client device 120 orthird-party device 130 to update a pilot's calendar to include anupcoming flight, and set reminders for the flight. Similarly, flightplanning system 110 and/or client device 120 may communicate withvarious other hardware, such as in-cockpit devices (e.g., instruments,wireless devices, computers, communication equipment, radar, etc.)associated with an aircraft, electronic engine monitoring systems, andpanel mounted navigation controls and devices, to upload or downloadflight trip data or the like. Flight planning system 110 may alsocommunicate with a client device 120 or third-party device 130 to updatea pilot's logbook to include up to date logbook information. Logbookinformation may include, for example, aircraft information, pilotinformation, flight information, departure information, destinationinformation, time, waypoints visited, fuel on board, passengers onboard, and/or any other information that is or is not required to belogged.

In one aspect, third-party device 130 may be a schedule organizer andmay receive flight plan and other information to update a calendar. Thecalendar may be stored on the third-party device, on client device 120,325, in memory 223, in database(s) 226, in user database 340, or in anyother data storage device associated with system 100. The calendar mayalso be linked with a user profile accessible through client device 120,325. The calendar may include entries containing information regardingevents associated with, for example, airports (e.g., scheduled closures,social events, fuel deliveries, etc.), aircrafts (e.g., scheduledmaintenance, recurring flights, etc.), and/or associated personnel. Inone aspect, the calendar may include information that may be used toplan a full trip, such as hotel reservations, local attractions,entertainment, points of interest, and/or other information. Suchinformation may be displayed on a calendar in a user interface, and theinformation may be displayed in coordination with received flight plantinformation (e.g., current location, destination location,current/future date and time, etc.) and/or other entries on thecalendar. Other content from other third-party sources may be included,as desired.

Calendar entries may be used to generate reminders. For example, areminder may be created on client device 120, 325 (e.g., visualreminders, graphical images, user interfaces, etc.) regarding ascheduled event prior to the event occurring. The reminder may beconfigured as a push notification or other type of visible reminder onclient device 120. As used herein, push notifications may includegraphical display overlays containing notification information that areautomatically generated by one or more processors, computing device, orclient devices. In this way, pertinent information may be brought to theuser's attention as the events become relevant based on time, location,and/or other ascertainable variables.

In another aspect, third-party device 130 may be configured to providetrip planning information to system 100. Trip planning information mayinclude, for example, hotel accommodations, commercial airfare, rentalcar information, restaurant information, attractions, points ofinterest, events, etc. Flight planning system 110 (e.g., in conjunctionwith one or more processors and/or other computing devices) may collecttrip planning information, via the API, from third-party device anddisplay the trip planning info on client device 120, 325. Flightplanning system may collect trip planning information in connection withflight planning information provided by the user or by an automaticallygenerated flight plan. For example, flight planning information, such asdeparture location, destination location, dates and times, future flightplans, and/or other information may be used by flight planning system110 to collect relevant trip planning information.

In another aspect, third-party device 130 may be a social media platformconfigured to receive information from flight planning system 110 and/orclient device 120, such as flight plans, pictures, schedules, locations,events, etc. Certain information may be automatically or conditionallysubmit the second request to the flight planning entity via the flightplanning system based on the user inputs. (e.g., based on a userpermission or preference, based on a category of information, etc.) sentto one or more social media platforms, such as calendar events, noticesof flight arrivals and/or departures (e.g., including time, date,location, etc.), flight plan details, and/or other information.

Further, in some embodiments, such as those in which a flight plan isgenerated, one or more of the components of system 100 may display,modify, update, manage, and/or configure the flight plan (step 460). Forexample, client device 120 may display the flight plan, which may allowa user to view and interact with the flight plan. For example, the usermay view a generated flight route, airport information (in variousformats such as full page, overlays, kneeboard, etc.), weatherinformation, etc. The user may select which information to view in aninteractive manner, which may include various charts, maps, and othergraphics that further enhance the flight planning experience.

In some embodiments, flight planning system 110 may continuously updateinformation provided to client device 120, such as by modifying theflight plan and/or providing additional features. For example, flightplanning system 110 may provide notifications (e.g., push notificationsin a mobile device) regarding temporary flight restrictions, changes inweather, news, airport changes, etc. Similarly, flight planning system110 may integrate newly received information into a flight plan orflight profile. For example, flight planning system 110 may communicatewith client device 120 or third-party device 130 to collect in-flightinformation, such as to maintain real-time information related to anongoing flight.

Further, in some embodiments, flight planning system 110 may provideflight information to a third-party device 130. For example, flightplanning system 110 may coordinate flight plan filing through an FAAauthorized filing agency (e.g., via flight plan API 318). Similarly,flight planning system 110 may provide information (e.g., via flightplan API 318) to integrate with third-party services, such as socialmedia, other flight planning services, weather services, etc., such asthrough communication with third-party devices 130 (or client device 120connected to a third-party device 130).

Consistent with disclosed embodiments, client device 120 may provide aninteractive flight plan or other flight information to a user. Theinteractive flight plan and available flight information may begenerated by flight planning system 110, which may have access to allinformation that may be pertinent to a flight through, for example, anetwork connection to internal and third-party systems via an API. Inthis way, pilots and other aviation personnel may request and receivecustomized flight information and interactive flight plans that serve asconvenient and comprehensive flight tools for use in preparing for andexecuting a flight, especially a general aviation flight. Further, theconnection with different types of client devices and variousthird-party devices allows for various formats (e.g., websites, mobileapplications, etc.) and thorough integration of flight information withother services. Further, the disclosed flight planning device may serveas an information warehouse for storing information related to pilots,crew, aircrafts, airports, custom waypoints, flight trip data,user-submitted information, etc.

While some features of flight plans produced by system 100 have beendescribed with respect to the above embodiments, it should be understoodthat they are not limited thereto, and that various other features maybe included or featured, depending on the information requested. Forexample, user-submitted content and information, such as photographs,messages, news articles, etc., may be received by system 100 inconjunction with capabilities of client devices 120, 325 and sharedbetween users through flight plans and other services. In one aspect,system 100 may be configured to display the user-submitted informationon at least one other device (e.g., another client device 120, 325, athird-party device 130, etc.). Pertinent information, such as fuelprices, flight tracking information, weight and balance information,etc., may also be made readily available from user-submittedinformation.

For example, a fueling tool may provide sortable fuel informationrelating to available fuel in certain areas (e.g., at a plurality ofairports, airport-affiliated suppliers, third-party suppliers, etc.) andinclude information posted by other users relating to fuel prices atcertain location. The fueling tool may include or provide access toinformation on various types of fuel available at particular locations,such as 100-LL (avgas), Jet A, MoGas (automotive grade), and others.Fuel information may be stored in a fuel database or other databasestored on one or more of client devices 120, 325 and server 211. Thefuel tool may also include search functionality to allow users toquickly find the location of desired fuel. For example, the fuel toolmay be a user interface configured to receive a request for fuelinformation. The user interface may include user forms, such as dropdownmenus, radio buttons, and text bars, which allow the user to searchand/or sort through (e.g., through filters) information by fuel type,price (e.g., maximum, minimum, range, etc.), distance (e.g., from acurrent location, along a route, from a destination, etc.), vendor type(e.g., public, private, etc.), or other information.

Various formats, such as kneeboard formats, may be created and used byclient device 120 to increase convenience for the pilot. For example,directory information and/or other information may be vied in full-pageviews, thumbnails, printable formats (e.g., kneeboard formats, fullpage, etc.), screen overlays, etc. Kneeboard formats may be configuredto generate information on documents sized to fit known or customkneeboard devices. Overlays may be positioned over other screens andinclude information relevant to the underlying screen. For example, anoverlay over screen showing a travel route may include informationindicative of, for example, fuel available along the route, airportsalong the route, airport services along the route, etc.

Tracking and aggregation of various flight-related information, data,events, and activities may also be available. For example, flightplanning system 110 may be configured to display on client device 120 agraphical tool, such as a graphical user interface or graphical overlay,configured to aggregate and show critical, pertinent, and/or relevantinformation relating to a flight. This graphical tool may be a widget,dashboard, or other type of graphical tool that allows a user to viewand or interact with pertinent data and/or command functionality. Thisgraphical tool may aggregate the most pertinent flight information fromone or more sources of information (e.g., third-party devices 130, anycomponent of flight planning system 110, client device 120, etc.)according to a default setting, a customized user setting, or programmedlogic that periodically or conditionally changes the types ofinformation displayed on the graphical tool. This graphical tool mayinclude flight trip data, aircraft data, pilot data, calendar data, andor other information. This graphical tool may display messages, notes,alerts, warnings, and/or push notifications to the user. Suchinformation may include messages from airports and authoritative bodies,messages from other aircraft, weather updates/warnings, breaking news,social media feeds, advertisements, and/or other information. Thisgraphical tool may be customizable to allow users to select the types ofinformation that appear on the graphical tool. All relevant informationdisplayed by this graphical tool may include all information relevant toa flight and available via network 140. Alternatively, all relevantinformation may include information selected for display according to adefault configuration, a customized or personalized configuration, orbased on control logic configured to prioritize information, overridedefault and customized/personalized settings, and/or generate pushnotifications.

Tracking and aggregation of other flight-related information may also beavailable. For example, flight planning system 110 may save a navigationlog, which may include detailed information such as altitude,frequencies, heading, winds, waypoints, intermediate and destinationairports, etc. Such information may be accessible for viewing inelectronic format or printable format (e.g., full view, kneeboardlayouts, etc.) and may be exportable via a wired communicationinterface, Wi-Fi, the Internet, a cellular network, etc.

The exemplary disclosed embodiments describe a comprehensive flightplanning tool. The foregoing description has been presented for purposesof illustration. It is not exhaustive and is not limited to the preciseforms or embodiments disclosed. Modifications and adaptations of theembodiments will be apparent from consideration of the specification andpractice of the disclosed embodiments. For example, the describedimplementations include hardware and software, but systems and methodsconsistent with the present disclosure can be implemented as hardwarealone.

Computer programs created on the basis of the written description andmethods of this specification are within the skill of a softwaredeveloper. The various programs or program modules can be created usinga variety of programming techniques. For example, program sections orprogram modules can be designed in or by means of Java, C, C++, assemblylanguage, or any such programming languages. One or more of suchsoftware sections or modules can be integrated into a computer system,computer-readable media, or existing communications software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication, which examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as example only, with a true scope and spirit being indicatedby the following claims and their full scope of equivalents.

1-20. (canceled)
 21. A system for providing a flight planning tool, comprising: at least one memory device; and one or more processors configured to execute instructions to perform operations comprising: providing via an Application Program Interface (API), communication between: the system and a client device; and the system and a third-party device; receiving, via the API, a request from the client device, the request comprising a user input indicative of first information related to a flight; requesting, via the API, second information from the third-party device, the second information being based on the first information; receiving the second information; generating supplemental flight plan information based on the user input and the second information; and displaying, via a user interface at the client device, a first graphic indicative of the supplemental flight plan information.
 22. The system of claim 21, wherein the supplemental flight plan information comprises information related to at least one of an airport, an aircraft, an airline, a pilot, social media, news, or an aviation entity.
 23. The system of claim 21, wherein the supplemental flight plan information comprises at least one of airport directory information, weight and balance information, temporary flight restriction information, user-generated content, logbook information, manual information, a calendar, communication frequency information, waypoint information, fuel statistics, date and time information, or Morse Code information.
 24. The system of claim 23, wherein the supplemental flight plan information comprises weight information related to at least one of passengers or cargo.
 25. The system of claim 24, wherein the weight information comprises weight information received from a sensor.
 26. The system of claim 25, wherein sensor comprises at least one of a contact sensor, a pressure sensor, an optical sensor, an infrared sensor, a barcode sensor, or a laser sensor.
 27. The system of claim 21, wherein the operations further comprise displaying a second graphic indicative of at least a portion of the first information.
 28. The system of claim 21, wherein the first information comprises information identifying at least one of a pilot, an aircraft, an origin, a destination, or a schedule.
 29. The system of claim 21, wherein the operations further comprise displaying a second graphic depicting a flight plan.
 30. The system of claim 29, wherein the second graphic depicts a flight route.
 31. The system of claim 21, wherein the operations further comprise displaying the first graphic as an overlay to an underlying graphic.
 32. The system of claim 31, wherein the underlying graphic comprises a graphic indicative of information associated with a flight plan.
 33. A method for providing a flight planning tool, comprising: providing, via an Application Program Interface (API), communication between: a system and a client device; and the system and a third-party device; receiving, via the API, a request from the client device, the request comprising a user input indicative of first information related to a flight; requesting, via the API, second information from the third-party device, the second information being based on the first information; receiving the second information; generating supplemental flight plan information based on the user input and the second information; and displaying, via a user interface at the client device, a first graphic indicative of the supplemental flight plan information.
 34. The method of claim 33, wherein the supplemental flight plan information comprises information related to at least one of an airport, an aircraft, an airline, a pilot, social media, news, or an aviation entity.
 35. The method of claim 33, wherein the supplemental flight plan information comprises at least one of airport directory information, weight and balance information, temporary flight restriction information, user-generated content, logbook information, manual information, a calendar, a communication frequency information, waypoint information, fuel statistics, date and time information, or Morse Code information.
 36. The method of claim 35, wherein the supplemental flight plan information comprises weight information related to at least one of passengers or cargo.
 37. The method of claim 36, wherein the weight information comprises information received from at least one of a contact sensor, a pressure sensor, an optical sensor, an infrared sensor, a barcode sensor, or a laser sensor.
 38. The method of claim 33, further comprising displaying a second graphic depicting a flight route.
 39. The method of claim 33, wherein the first graphic is displayed as an overlay to an underlying graphic.
 40. The method of claim 39, wherein the underlying graphic is indicative of information associated with a flight plan. 